We were unable to load Disqus. If you are a moderator please see our troubleshooting guide.

Reactions
16 Responses
Upvote
 
Upvote
Funny
 
Funny
Love
 
Love
Surprised
 
Surprised
Angry
 
Angry
Sad
 
Sad
Avatar
Join the discussion…


  • in this conversation
      Media preview placeholder
      Log in with
      or sign up with Disqus or pick a name

      • Avatar

        Hello all,

        First of all, I feel truly sorry that you feel disappointed by this release. This actually comes as a surprise to me as I didn’t hear many negative comments since the beta went out back in June.

        According to our metrics, there are over 170,000 shops running 1.7, and the adoption rate of 1.7.8 is similar to our previous versions, which is to say, fast. The majority of shops we know of are running recent versions, which is a good sign. I struggle to see how anyone could qualify that as a "disaster”: if people are using it, I’m pretty sure that it must mean that it works well enough for them.

        PrestaShop has bugs, like literally any other software on Earth. Could it be better? Of course. But only if everyone rolls up their sleeves and collaborate on it. This is an open source project, out of the 168 people that collaborated on 1.7.8, only 27 were affiliated with the company. However, almost 80% of the merged Pull Requests were financed by the company. We need people to participate more so that the project can improve faster.

        Contrary to what some said, the Core teams are actually excellent, and have my highest regard. They work tirelessly to improve PrestaShop, by writing specifications, fixing issues, writing tests, and manually verifying changes.

        PrestaShop has one of the most thorough QA process I have seen in open source projects, where every single Pull Request is reviewed by two developers and has to pass both automated CI and manual QA verification. Where every night there’s a 4-hour long automated functional test suite, and a fully automated upgrade test. Where each build passes a week-long battle test by the QA before it’s published. Where there’s a month-long public beta, and a public release candidate for every minor release.

        Here’s what you can do to help improve the project: report issues (especially during the beta period), contribute fixes (or pay someone else to do it for you), help test pull requests, and finally, discuss solutions on slack.

        (Note: some comments have been hidden because they were disrespectful to the people who work at PrestaShop. Read our Code of Conduct for more.)

        • Avatar

          Hi,
          This new version is still really a big disappointment.
          It still affects my default theme that has been somewhat modified with custom CSS.
          It happens even though I have chosen NO to upgrade the default theme the 1-click-upgrade.
          I did not happen before when upgraded within 1.7.7.x

          Please make sure the next update does not affect theme when you release the next update.
          Sorry to say this, but I am not so sure now about the future of prestashop. Already exploring other platforms such as woocommerce.
          Tks.

          • Avatar

            Hello, it's complicated to maintain a free CMS.

            How to pay full time developers to take care only of Prestashop?

            Maybe Prestashop should be paid so that a team can be totally dedicated to solve the problems.

            Currently we wait for a problem to arise in order to work on a patch, then wait to test it and adapt it again and again... All this on a voluntary basis, in addition to his daily work.
            And it takes ...some time :-)

            Fortunately many developers like this free opensource system... And participate (look on GitHub).

            By switching to WP or other you will find the same problems if you stay in a free model...

            Then, to not have any problem you just have to pay a developer to maintain Prestashop permanently at the top of the top and there, it works well.

            But in the current model, there will always be bugs ... To correct.

            Let's be positive, we already have one of the best online store management system. The most accessible to a beginner. And the most open to developers.
            Of course we need everyone to earn money, but it's hard to earn money without spending money...

            And I'm happy to continue to participate

            Thanks again to the whole Prestashop ecosystem.

            https://media4.giphy.com/me...

              see more
              • Avatar

                Actually Prestashop is not free! - Prestashop make profit from modules sold/used, various services/subscriptions, and I believe also kick-back from ads spend through their Google Ads / Facebook modules etc.

                There will always be bugs! if a paid solution seems to have less bugs, it is usually because not many improvements are being made either :-)

                For me, the biggest problem with Prestashop is the Quality Assurance (QA). It often take several attempts to fix bugs, and everytime something is fixed, it seem to introduce new problems.

                Way too litle testing is going on before releases. I have previously suggested, that when a bug is reported (Github), the poster(s) should also be actively involved in testing and approving the fix prior to final release. This would help reducing repeating bugs and fixing time.

                • Avatar

                  Hi, If you want to make prestashop a paid e-commerce and can make it better. Go ahead, why not?
                  Why continuously moving with flawed update? Don't keep using "free CMS" as an excuse. Make prestashop a paid one. Go ahead!!

                • Avatar

                  Keep going, thanks!